Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0140

reference: 186-tree-1
name: 0140
tree-preservation-order: undefined
186-tpo-1
uprn
address-text
point: POINT (-0.939284 50.864483)
geometry: MULTIPOLYGON (((-0.939255 50.864480,-0.939256 50.864485,-0.939260 50.864490,-0.939274 50.864497,-0.939283 50.864498,-0.939300 50.864495,-0.939306 50.864491,-0.939310 50.864486,-0.939312 50.864480,-0.939311 50.864475,-0.939307 50.864470,-0.939301 50.864466,-0.939293 50.864463,-0.939284 50.864462,-0.939267 50.864465,-0.939261 50.864469,-0.939257 50.864474,-0.939255 50.864480)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL